Push Notifications

Description

Native push notifications overview and all of the component templates that have been created to demonstrate the use of the numerous push notification plugins.

Name
Description
Push Notifications : Pushwoosh Component Template

This component template demonstrates the use of the Pushwoosh plugin which enables sending and receiving push notifications powered by Pushwoosh.

Push Notification Overview

When a native mobile app is registered to process push notifications, the app does not need to be running in order to receive and display the notification. The notification messages are sent from a server back end and received by the device without an explicit request from the device or user. A user must agree to accept notifications from the app but once that is done, the notifications will arrive without the device initiating a request. Depending upon the device, the notification can cause the phone to beep or vibrate and it may display a message either within the app (if it is active and has focus) or as a toast pop-up or across the top of the screen. The message may contain a badge, text, a hyperlink, etc. Typically if the user taps on the message (assuming he/she is not in the app), the app will launch or transition into view.

Push Notification Architecture

Push notification processing is platform specific. The process of subscribing to push notifications is very different for iOS, Android and Windows devices. Each platform requires a different push notification dispatch server and each platform requires it's own unique method of app authentication and authorization for push notifications. Security is paramount. Apple, Google and Microsoft provide platform specific push notification servers (PNS) to communicate with their respective devices. At this point in time, access to these servers is free of charge. If you as a developer want to write the application specific server side code that can communicate with each of these platform specific push notification servers, you can. Of course you must be well versed in the specifics of each PNS.

Apple uses the Apple Push Notification Service (APNS) which can send notifications to iOS (and indirectly to watchOS), tvOS and OS X devices.

Apple Push Notification Service (APNS)

images/apns.png

Google uses Google Cloud Messaging (GCM) which can send notifications to Android devices or to the Google Chrome Internet browser.

Google Cloud Messaging

images/gcm.png

Windows uses the Windows Push Notification Service (WNS) which can send notifications to Windows 8, Windows 8.1, Windows Phone 8.1, Windows 10, Windows 10 Mobile and XBox.

Windows Push Notification Services (WNS)

images/wns.png

Cross Platform Push Notification Services

If you are planing to support multiple devices/platforms, you should consider using a cross platform push notification service. These offer a standard API for their service which in turn processes and sends the push notifications to the respective platform specific servers. As such, with one API you can send messages to Android, iOS and Windows devices.

There are a number of cross platform push notification service providers, each with unique features. There is typically a usage or monthly charge for these services.

Some of the cross platform push notification service providers include:

  1. Amazon Simple Notification Service (SNS)

  2. Bit6 IP Messaging

  3. Google Cloud Messaging

  4. Microsoft Azure Notification Hub

  5. Pushwoosh

We are continually working on numerous component templates that support different cross platform push notification services. If you do not see the service you are interested in exploring in the component template list at the top of this page at the present time, check back at a later date for a possible update.